Surfacing Task-Related Applications in a Heterogeneous Tab Environment

ABSTRACT

Techniques for surfacing task-related applications in a heterogeneous tab environment are described. In at least some implementations, a task group is created based on an implicit association between source content from a source application and target content from a target application based on a request to launch the target application from the source application. According to various implementations, the heterogeneous tab environment presents the task group and a trigger event is defined based on the task group. Detecting the trigger event causes surfacing of the task group in the tab environment.

RELATED APPLICATION

This application claims priority under 35 U.S.C. Section 119(e) to U.S.Provisional Patent Application No. 62/487,373, filed Apr. 19, 2017 andtitled “Resurfacing Task-Related Applications in a Heterogeneous TabEnvironment,” the entire disclosure of which is hereby incorporated byreference herein.

BACKGROUND

Conventionally, users who seek to resume a task that requires to accessto more than one application are required to individually open each itemin each application. For example, a user reading e-mail in an e-mailapplication opens an attachment and the attachment launches in an imageviewing application. At a later time, the user wishes to resume a taskinvolving the e-mail and attachment and must launch each applicationagain. Enabling surfacing of heterogeneous content generally requiresexplicit user setup, such as via a custom script.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Techniques for surfacing task-related applications in a heterogeneoustab environment are described. In at least some implementations, a taskgroup is created based on an implicit association between contentlaunched to a target application from a source application. According tovarious implementations, a tab environment is launched presenting boththe source application and the target application. Thus, receiving atrigger event causes subsequent surfacing of the task group in the tabenvironment for interaction with the heterogeneous content in a singleshell interface.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of an environment in an example implementationthat is operable to employ techniques discussed herein.

FIG. 2 depicts an example implementation scenario for creating a taskgroup and launching a heterogeneous tab environment in accordance withone or more embodiments.

FIG. 3 depicts an example implementation scenario for updating a taskgroup in accordance with one or more embodiments.

FIG. 4a depicts an example implementation scenario for surfacing a taskgroup in a heterogeneous tab environment in accordance with one or moreembodiments.

FIG. 4b depicts an example implementation scenario for surfacing a taskgroup in more than one instance of a heterogeneous tab environment inaccordance with one or more embodiments.

FIG. 5 depicts an example implementation scenario for creating a taskgroup from task-related interaction in accordance with one or moreembodiments.

FIG. 6 is a flow diagram that describes steps in a method for creatingand surfacing a task group in accordance with one or more embodiments.

FIG. 7 is a flow diagram that describes steps in a method for creating atask group in a heterogeneous tab environment in accordance with one ormore embodiments.

FIG. 8 is a flow diagram that describes steps in a method for creating atask group from task-relates interaction in accordance with one or moreembodiments.

FIG. 9 illustrates an example system and computing device as describedwith reference to FIG. 1, which are configured to implement embodimentsof techniques described herein.

DETAILED DESCRIPTION

Implementations discussed herein enable surfacing task-relatedapplications in a heterogeneous tab environment. The describedtechniques, for instance, enable creating and surfacing a task group ina tab environment. In an example implementation, a client devicepresents a source application with source content that includes a visualindicator selectable to launch target content in a target application. Auser selects the visual indicator, such as a document attachment, fromthe source application and a request is generated. The request causes aheterogeneous tab environment to be presented including a tab populatedby the source application and a tab populated by the target application.A task group is then created to include the source content and thetarget content based on an association between the source content andthe target content indicated by the request. To enable the task group tobe recreated, a trigger event is defined for surfacing the task group ina heterogeneous tab environment. The trigger event may be defined invarious ways, such as an indication of a request to launch the targetcontent or the source content.

In some instances, the user opens additional relevant content in the tabenvironment while the source content and/or the target content arepresented. As a result, the task group is updated to include theadditional relevant content and the trigger event is updated based onthe additional relevant content. When the trigger event is subsequentlydetected, the task group is surfaced in the heterogeneous tabenvironment. For instance, consider that after the heterogeneous tabenvironment is closed, the user selects the target content forpresentation. This fires the trigger event, which causes a heterogeneoustab environment to be presented (“surfaced”) with the task group. Thus,content from disparate sources is associated as a task group to enablethe content to be surfaced in a tab environment at a later time.

Generally, surfacing a task group in a heterogeneous tab environmentallows for interaction with associated content from heterogeneoussources in a single shell interface. Thus, techniques described hereinsimplify interactions with associated content by providing a user withassociated content from a task group of heterogeneous sources in asingle, intuitive shell and without requiring the user to remember andindividually launch each instance of the associated content in the taskgroup.

Having presented an overview of techniques for surfacing task-relatedapplications in a heterogeneous tab environment, consider now an exampleenvironment in which techniques described herein may be implemented.

FIG. 1 is an illustration of an environment 100 in an exampleimplementation that is operable to employ techniques for surfacingtask-related applications in a heterogeneous tab environment discussedherein. Environment 100 includes a client device 102, which can beembodied as any suitable device such as, by way of example and notlimitation, a smartphone, a tablet computer, a portable computer (e.g.,a laptop), a desktop computer, a wearable device, and so forth. In atleast some implementations, the client device 102 represents a smartappliance, such as an Internet of Things (“IoT”) device. Thus, theclient device 102 may range from a system with significant processingpower, to a lightweight device with minimal processing power.Additionally, although a single computing device is shown in someinstances, the client device 102 may be representative of a plurality ofdifferent devices, such as other client device(s) 104 capable ofcommunicating over a network 106. The other client device(s) 104, whichcan be embodied as any suitable device, are generally representative ofa plurality of different devices capable of communicating with theclient device 102 over the network 106. One of a variety of differentexamples of the client device 102 and/or the other client device(s) 104is shown and described below in FIG. 9.

The network 106 is representative of a network that provides the clientdevice 102 with connectivity to various networks and/or services, suchas the Internet. The network 106 may provide the client device 102 withconnectivity via a variety of different connectivity technologies, suchas broadband cable, digital subscriber line (DSL), wireless cellular,wireless data connectivity (e.g., WiFi™) T-carrier (e.g., T1), Ethernet,and so forth. In at least some implementations, the network 106represents different interconnected wired and wireless networks. Thenetwork 106 may be implemented in various ways, such as a local accessnetwork (LAN), a wide area network (WAN), the Internet, and so forth.According to various implementations, the network 106 provides theclient device 102 with access to network services 108.

The network services 108 are generally representative of a network-basedfunctionality for providing data and services to the client device 102over the network 106. The data and services provided by the networkservices 108 can include any suitable combination of data and/orservices typically made available over a network such as the network106. Some examples of services include, but are not limited to, anonline computing service (e.g., “cloud” computing), an authenticationservice, web-based applications, a file storage and collaborationservice, a search service, messaging services such as email, text and/orinstant messaging, a social networking service, and so forth. Servicesprovided by the network services 108 may also include locationinformation services, which can determine a location of the clientdevice 102, based on an identity of a network and/or network componentwith which the client device 102 is in communication. Examples oflocation information include global positioning system (GPS)coordinates, street addresses, network location, location with referenceto cell towers and/or cellular base stations, and so forth.

The client device 102 includes a variety of different functionalitiesthat enable various activities and tasks to be performed. For instance,the client device 102 includes an operating system 110 and applications112. Generally, the operating system 110 is representative offunctionality for abstracting various system components of the clientdevice 102, such as hardware, kernel-level modules and services, and soforth. The operating system 110, for instance, can abstract variouscomponents of the client device 102 to the applications 112 to enableinteraction between the components and the applications 112.

The applications 112 represent functionalities for performing differenttasks via the client device 102. Examples of the applications 112include a word processing application, a spreadsheet application, a webbrowser, a gaming application, and so forth. The applications 112 may beinstalled locally on the client device 102 to be executed via a localruntime environment, and/or may represent portals to remotefunctionality, such as cloud-based services, web apps, and so forth.Thus, the applications 112 may take a variety of forms, such aslocally-executed code, portals to remotely hosted services, and soforth.

The applications 112 include a source application 114 and a targetapplication 116. The source application 114 generally represents anapplication with which a user 118 may interact to view and manipulatecontent in various ways. In at least some implementations, some of thecontent presented by the source application 114 opens via a differentapplication, e.g., the target application 116. The target application116, for example, represents an application, which launches as a resultof interaction with content in the source application 114.

The client device 102 further includes a display device 120 and inputmechanisms 122. The display device 120 generally representsfunctionality for visual output for the client device 102. Additionally,the display device 120 represents functionality for receiving varioustypes of input, such as touch input, pen input, and so forth.

The input mechanisms 122 represent different functionalities forreceiving input to the client device 102. Examples of the inputmechanisms 122 include touch input devices, touchless input devices,gesture-sensitive sensors and devices (e.g., such as touch-based sensorsand movement-tracking sensors (e.g., camera-based)), a mouse, akeyboard, a stylus, a touch pad, accelerometers, a microphone withaccompanying voice recognition software, and so forth. The inputmechanisms 122 may be separate or integral with the display device 120;integral examples include gesture-sensitive displays with integratedtouch-sensitive or motion-sensitive sensors.

The client device 102 further includes a task group module 124, which isrepresentative of functionality to perform various actions pertaining tocreating, maintaining, and surfacing task groups discussed herein. Thetask group module 124, for instance, can be leveraged to create andmaintain groups of heterogeneous content accessed by the user 118 toenable the user 118 to surface the content in a convenient and intuitivemanner, such as in a heterogeneous tab environment (“tab environment”)126. For example, the task group module 124 associates concurrentlyactive content as a task group to enable surfacing the heterogeneouscontent in a convenient interface. Various attributes and operationalaspects of the task group module 124 are detailed below.

In implementations, the task group module 124 can manage, control,and/or interact with the operating system 110 and/or a tab environmentmodule 128 of the client device 102 to enable the techniques forcreating, maintaining, and surfacing task groups described herein. Thetask group module 124, for example, may provide selective modificationto a user experience (“UX”) based on task groups in the tab environment126.

The task group module 124 maintains task group policies 130, which arerepresentative of different sets of data that specify criteria (e.g.,permissions, rules, and so forth) for collecting, aggregating,maintaining, and/or presenting task-related content for the user 118.The task group module 124, for instance, causes the tab environmentmodule 128 to present task group content in the tab environment 126based on the content collected and aggregated in accordance with thetask group policies 130. Thus, the task group policies 130 can beleveraged to specify which content to collect, aggregate, and/orpresent, as well as how to configure content for presentation.Alternatively or additionally, the task group policies 130 are contentand/or application-specific. Further, the task group policies 130 mayspecify privacy settings for the user 118 regarding collection and/oraggregation of content accessed by the user 118. Generally, the taskgroup policies 130 can be configured in various ways such as via defaultsettings, settings specified by a user, by information technology (IT)personnel, by application development personnel, and so forth.

The task group module 124 further maintains trigger event policies(“trigger policies”) 132, which are representative of different sets ofdata that specify criteria (e.g., permissions, rules, and so forth) forsurfacing task-related content for the user 118. The trigger policies132, for instance, specify which input, occurrence, behavior, event, andso forth causes the task group module 124 to surface the task-relatedcontent for the user 118. In at least some implementations, the triggerpolicies 132 are content and/or application-specific. For instance, thetrigger policies 132 may specify contextual data related to the taskand/or the user 118 to include for identifying a trigger event. Examplesof the contextual data include date, time, location, device type, and soforth.

By including the contextual data related to the task and/or the user 118for identifying the trigger event, the task group module 124 is able tosurface task-related content to the user 118 in appropriate and relevantcircumstances. The trigger policies 132 may specify that the task groupmodule 124 obtain data from the network services 108 over the network106 to identify and/or detect a trigger event. For instance, consider anexample implementation where the task group module 124 identifies that atrigger event occurs upon detecting that the user 118 is at the closestairport. To enable the task group module to detect the location of theuser 118, the trigger policies 132 specify that data indicating thegeographical location of the client device 102 be obtained from thenetwork services 108 over the network 106. Generally, the triggerpolicies 132 can be configured in various ways such as via defaultsettings, settings specified by a user, by information technology (IT)personnel, by application development personnel, and so forth.

The tab environment module 128 is representative of functionality forpresenting the tab environment 126 and is capable of integrating contentfrom heterogeneous sources into a single interactive shell interface.Generally, content may take a variety of forms, such as variouscombinations of the applications 112, services, text, multi-mediastreams, documents, application files, photos, audio/video files,animations, images, web pages, web applications, content for display bya browser or other client application, data structures, self-executingcontent, local content, remote content, application interfaces for theapplications 112, and so forth. As used herein, heterogeneous contentmay refer to any combination of the various types and/or forms ofcontent listed above including content of the source application 114,the target application 116, and/or other examples of the applications112. While the tab environment module 128 is described herein aspresenting the tab environment 126 in a single shell interface, itshould be understood that the tab environment module 128 is capable ofpresenting the tab environment 126 in multiple separate shell interfacesas may be appropriate and/or convenient.

The tab environment module 128 maintains application launch settings(“launch settings”) 134, which are representative of different sets ofdata that specify criteria (e.g., permissions, rules, and so forth) formanaging launch and execution of the applications 112 in the tabenvironment 126. Generally, the launch settings 134 enable theapplications 112 to be presented in the tab environment 126 withoutsacrificing aesthetic or functional aspects of native interfaces for theapplications 112. The launch settings 134, for instance, indicatedifferent behaviors that can be applied to different launch scenariosfor the applications 112. Examples of the different behaviors applied tothe applications 112 include adding, switching, positioning, sizing, andmanipulating tabs 136 in the tab environment 126 and/or visualinterfaces of the applications 112. Further, the launch settings 134 canenforce behaviors for the applications 112 based a particular devicetype and/or execution platform on which the applications 112 arelaunched. Alternatively or additionally, the launch settings 134 arecontent and/or application-specific.

In at least some implementations, the tab environment module 128generates the tab environment 126 to enable the user 118 to interactwith tabbed instances of heterogeneous content, including one or more ofthe applications 112. The tab environment 126 generally represents afunctional collection of interaction affordances that can be configuredin various ways according to techniques for a heterogeneous tabenvironment described herein. The tab environment 126 can be useful in avariety of settings, such as where the user 118 interacts with contentfrom heterogeneous sources. In at least some implementations, the tabenvironment 126 may be implemented as a desktop, virtual or otherwise,and include various controls via interactive elements, menus, and soforth.

As depicted in the environment 100, the tab environment 126 includestabs 136, which include a tab 136 a, a tab 136 b, and a tab 136 c.Further, the tabs 136 are presented within a graphical user interface(“GUI”) 138 that is output on the display device 120 by the tabenvironment module 128 to employ heterogeneous tab environmenttechniques described herein. Each of the tabs 136 can present differentinstances and/or types of content, thus affording interaction withheterogeneous content in a convenient manner, such as in a single shellinterface. For instance, the tabs 136 can be populated by the sourceapplication 114 and/or the target application 116, as well as withcontent of the source application 114, target application 116, and/orthe applications 112, and so forth. Generally, the tabs 136 representindividual shell interface frames presented within a single visual shellof the GUI 138 to enable quick and easy access to varied content viavisual and selectable tabs in the shell, e.g., the tabs 136. While threeof the tabs 136 are depicted, it should be understood that more or lessthan three of the tabs 136 may be presented in the tab environment 126.

By configuring the GUI 138 in the various ways described herein, the tabenvironment module 128 enables the user 118 to interact with contentfrom heterogeneous sources through a single interface shell or multipleshell interfaces. According to various implementations, the GUI 138 canbe implemented by the tab environment module 128 and can be madeavailable to different devices associated with the user 118, such as theclient device 102 and the other client device(s) 104. Regardless ofwhere the GUI 138 is used, the GUI 138 is generally representative of alocation to promote quick and easy interaction with heterogeneouscontent.

In this environment, the user 118 represents a single user associatedwith the tab environment 126, but it will be appreciated that more thanone user may interact with the tab environment 126 and/or the GUI 138.

Having described an example environment in which the techniquesdescribed herein may operate, consider now a discussion of some exampleimplementation scenarios in accordance with one or more embodiments. Theimplementation scenarios may be implemented in the environment 100discussed above, and/or any other suitable environment.

FIG. 2 depicts an example implementation scenario 200 for creating atask group and launching a heterogeneous tab environment in accordancewith one or more implementations. The scenario 200 includes variousentities and components introduced above with reference to theenvironment 100.

In the scenario 200, the user 118 interacts with source content 202 ofthe source application 114 presented on the GUI 138. The source content202 includes a visual indicator 204 which is selectable from the sourceapplication 114 to launch the target application 116. The visualindicator 204, for instance, is representative of selectablefunctionality for invoking the target application 116. For example, thevisual indicator 204 may represent an access protocol, e.g., a uniformresource locator (URL) or uniform resource indicator (URI). Additionallyor alternatively, the visual indicator 204 may represent a launchprotocol, e.g., a file type, application launch protocol, a selectableicon, and so forth.

Further to the scenario 200, the user 118 selects the visual indicator204, which causes the source application 114 to generate a request 206.In at least some implementations, the selection of the visual indicator204 is received via the input mechanisms 122. For instance, the user 118selects the visual indicator 204 via a touch input, e.g., the inputmechanisms 122.

The tab environment module 128 receives the request 206 from the sourceapplication 114 to launch the target application 116. Accordingly, andproceeding to the lower portion of the scenario 200, the tab environmentmodule 128 causes the target application 116 to launch with targetcontent 208. The request 206 generally includes various informationpertaining to the target content 208, such as an identifier, a filetype, an application launch protocol, and so forth.

To present the target content 208, the tab environment module 128presents the tab environment 126 with the tab 136 a and the tab 136 b inthe GUI 138, as depicted in the lower portion of scenario 200. In someimplementations, the launch settings 134 specify that the tabenvironment module 128 present the tab environment 126 in the shellinterface of the source application 114. In an alternativeimplementation, the tab environment module 128 presents the tabenvironment 126 in a new shell interface, replacing the shell interfaceof the source application 114.

In the scenario 200, the tab environment module 128 populates the tabs136 a and 136 b with the source application 114 and the targetapplication 116, respectively. The tab environment 126, for instance, ispopulated according to the launch settings 134 to display the targetcontent 208 in the tab 136 b. Generally, the tabs 136 a, 136 b areindividually selectable to switch visual focus between the sourcecontent 202 and the target content 208. For instance, selecting the tab136 a causes the source content 202 to be presented in the foreground,and selecting the tab 136 b causes the target content 208 to bepresented in the foreground, such as to replace the source content 202in the GUI 138.

Continuing with the scenario 200, the task group module 124 receives therequest 206 and creates a task group 210 in response to receiving therequest 206. The task group 210 generally represents heterogeneouscontent (e.g., the source content 202 and the target content 208)associated with each other by the task group module 124 as a result ofinteraction of the user 118 with the source content 202. In the scenario200, the task group 210 is created to include the source content 202 andthe target content 208 based on the task group module 124 receiving therequest 206. Thus, the task group 210 enables heterogeneous content,e.g., the source content 202 and the target content 208, to beassociated in a task-related manner based on receiving the request 206to open content from a heterogeneous source, such as the request 206 toopen the target application 116 from the source application 114.Alternatively or additionally, the task group 210 is created in responseto an explicit request from the user 118 to create the task group 210.

Based on the task group 210, the task group module 124 defines a triggerevent 212 in accordance with the trigger policies 132 for surfacing thetask group 210. Generally, the trigger event 212 specifies one or moreevents that trigger the task group module 124 to surface the task group210 to the tab environment module 128 for presentation in the tabenvironment 126. In accordance with the trigger policies 132, the taskgroup module 124 can utilize various types of data for defining thetrigger event 212, such as the source content 202, the target content208, time-based events, location tracking, device type, input type, andso forth. According to various implementations, the task group module124 defines the trigger event 212 to include detecting a request tolaunch the source content 202 and/or the target content 208. Forinstance, and as detailed below, the task group module 124 defines thetrigger event 212 to include receiving an input at a URI configured tolaunch the target content 208 in the target application 116. By definingthe trigger event 212 to include a request to present content from thetask group 210, the task group module 124 is able to surface the taskgroup 210 for the user 118 in a relevant context.

FIG. 3 depicts an example implementation scenario 300 for updating atask group in accordance with one or more implementations. The scenario300 includes various entities and components introduced above withreference to the environment 100 and the scenario 200, and in at leastsome implementations represents an extension of the scenario 200.

In the scenario 300, the tab environment 126 is presented including thetab 136 a populated by the source application 114, the tab 136 bpopulated by the target application 116, and the tab 136 c populated byadditional relevant content 302. The relevant content 302 generallyrepresents content, which is presented while with the tab 136 a ispopulated with the source content 202 and/or the tab 136 b is populatedwith the target content 208. In at least some implementations, the user118 opens the relevant content 302 in the tab 136 c while the tabs 136 aand/or 136 b are populated by the source content 202 and/or the targetcontent 208, respectively.

For instance, consider an example where the source application 114 is atax preparation application populating the tab 136 a and the user 118opens a web browser application (e.g., another instance of theapplications 112) in the tab 136 c to interact with the relevant content302, in this case a tax form. The task group module 124 updates the taskgroup 210 to include the relevant content 302 populating the tab 136 c.For example, the task group module 124 sends a query to the tabenvironment module 128 and the tab environment module 128 identifies therelevant content 302. Continuing with the example scenario, the taskgroup 210 is updated to include the relevant content 302, i.e., the taxform opened by the user 118 in the tab 136 c. Thus, the tax form (e.g.,the relevant content 302) is associated with the tax preparationapplication (e.g., the source content 202) by the task group module 124based on both the relevant content 302 and the source content 202 beingconcurrently presented in the tab environment 126.

According to at least some implementations, the task group 210 isupdated in response to the task group module 124 receiving an indicationthat the source content 202 and the target content 208 are no longerpresented in the tab environment 126. To update the task group 210, thetask group module 124 queries the tab environment module 128 for therelevant content 302. For example, the tab 136 a populated by the sourceapplication 114 and the tab 136 b populated by the target application116 are both closed and the task group module 124 queries the tabenvironment module 128 for any content presented in the tab environment126 with the source content 202 and/or the target content 208, e.g., therelevant content 302. The source content 202 and the target content 208may cease to be presented in the tab environment 126 for variousreasons. Examples of such reasons include closing of the tabs 136 aand/or 136 b by the user 118, closing of the tabs 136 a and/or 136 b bythe tab environment module 128, closing of the tab environment 126 bythe user 118, closing of the tab environment 126 by the tab environmentmodule 128, closing of the tab environment 126 by the operating system110, and so forth. In an alternative implementation, the task groupmodule 124 queries the tab environment module 128 for the relevantcontent 302 responsive to receiving an indication that the tab 136 c ispopulated while the source content 202 and/or the target content 208populate the tab environment 126.

In response to updating the task group 210, the task group module 124updates the trigger event 212 to account for the updated task group 210.For instance, the trigger event 212 is updated to include receiving arequest to launch the relevant content 302 as an additional instance ofthe trigger event 212.

While the relevant content 302 is depicted as content of an application112 populated to the tab 136 c, it should be understood that any numberof the tabs 136 of the tab environment 126 may be populated with therelevant content 302. The relevant content 302 may include theapplications 112 or any other type of content presentable in the tabenvironment 126. In some implementations, the relevant content 302 maybe a different instance of the source application 114 or the targetapplication 116.

FIG. 4a depicts an example implementation scenario 400 a for surfacing atask group in a heterogeneous tab environment in accordance with one ormore implementations. The scenario 400 a includes various entities andcomponents introduced above with reference to the environment 100 andthe scenarios 200, 300, and in at least some implementations representsan extension of the scenarios 200, 300.

In the scenario 400 a, the task group module 124 receives an indicationof the trigger event 212 and surfaces the task group 210 to the tabenvironment module 128 in response. The trigger event 212, for example,is received by the task group module 124 as a result of the user 118selecting the target content 208 for presentation. Responsive toreceiving the trigger event 212, the task group module 124 sends thetask group 210 to the tab environment module 128 for presentation.

Consider an example where the task group 210 includes the relevantcontent 302, the source content 202, and the target content 208, all ofwhich are related to tax preparation activities. In accordance with thetask group policies 130, the task group module 124 determines that thetask group 210 relates to tax preparation, such as based on keywordrecognition within the task group 210. Continuing the example, the taskgroup module 124 defines the trigger event 212 to include a time-basedevent such as a calendar date one week prior to a tax filing deadlinefor the user 118, and specifying that the task group module 124 is toobtain calendar and/or date information from the network services 108 inorder to enable detection of the trigger event 212. As a result, thetrigger event 212 occurs on the date specified by the task group module124, e.g., one week before the tax filing deadline. The occurrence ofthe date specified by the trigger event 212 causes the task group module124 to detect the trigger event 212. In response to detecting thetrigger event 212, the task group module 124 surfaces the taxpreparation-related content of the task group 210 to the tab environmentmodule 128 for presentation to the user 118 in the tab environment 126.In scenarios such as the example described, the task group module 124uses the trigger event 212 to define whether and/or when to surface thetask group 210. In this manner, the trigger event 212 enables the user118 to access a relevant group of tabs in a single shell interface,e.g., the tab environment 126, based on a relevant context for the user118.

Continuing with the scenario 400 a, the tab environment module 128receives the task group 210 from the task group module 124 and presentsthe task group 210 in the tab environment 126. For instance, the tabs136 a, 136 b, and 136 c of the tab environment 126 are populated by thesource application 114, the target application 116, and the relevantcontent 302, respectively. In at least some implementations, a visualprompt 402 is presented to the user 118 by the task group module 124and/or the tab environment module 128 in response to the task groupmodule detecting the trigger event 212. Generally, the visual prompt 402is selectable to cause presentation of all or part of the task group 210in the tab environment 126. For instance, the visual prompt 402 may bepresented as an interactive control configured to display selectablerepresentations of each instance of the source content 202, the targetcontent 208, and the relevant content 302 as individually selectable andselectable as a group for presentation in the tab environment 126.

According to various implementations, the task group 210 is presented ina new instance of the tab environment 126. For instance, the task groupmodule 124 created the task group 210 in association with a firstinstance of the tab environment 126 which was later closed, and the taskgroup 210 is surfaced in a new instance of the tab environment 126. Inat least some implementations, the trigger event 212 is detected overthe network 106 and/or at other devices. For example, the trigger event212 is detected by the task group module 124 from the other clientdevice(s) 104 as a result of the user 118 selecting the source content202 for presentation on the other client device(s) 104. Accordingly, thetask group 210 is presented in a new instance of the tab environment 126and on a different device, e.g., on an instance of the other clientdevice(s) 104.

In at least one implementation, an application 112 to be populated tothe tab environment 126 is not immediately available for executionand/or presentation in the tab environment 126. For example, the targetapplication 116 is not installed on the client device 102. Accordingly,the tab environment module 128 may cause download and/or installation ofthe target application 116, such as from the network services 108 overthe network 106. In some implementations, download and/or installationof content to enable presentation of the task group 210 may occurautomatically in response to the trigger event 212 and/or in response tosurfacing the task group 210. Additionally and alternatively, downloadand/or installation of content may occur responsive to explicitpermission from the user 118 such as via a prompt, e.g., the visualprompt 402.

While the tab environment 126 is described above as a single shellinterface, it should be understood that in at least some implementationsthe task group 210 is surfaced in more than one shell interface of thetab environment 126, such as in the scenario 400 b described below.

FIG. 4b depicts an example implementation scenario 400 b for surfacing atask group in more than one instance of a heterogeneous tab environmentin accordance with one or more implementations. The scenario 400 bincludes various entities and components introduced above with referenceto the environment 100 and the scenarios 200, 300, 400 a, and in atleast some implementations represents an extension of and/or alternativeto the scenarios 200, 300, and 400 a.

In the scenario 400 b, the tab environment module 128 receives the taskgroup 210 from the task group module 124 and presents the task group 210in the tab environment 126 as separate shell interfaces 404 of the tabenvironment 126, depicted in the scenario 400 b as shell interface 404 aand shell interface 404 b. For example, a first portion of the tabenvironment 126 is presented in the shell interface 404 a with the tabs136 a and 136 b populated by the source application 114 and the targetapplication 116, respectively. Further, a second portion of the tabenvironment 126 is presented in the shell interface 404 b with the tab136 c populated by the relevant content 302. Generally, when the taskgroup 210 is surfaced via the shell interfaces 404 a, 404 b, the shellinterfaces 404 a, 404 b may be presented in a number of ways such aspartially overlapping shell interfaces, side-by-side shell interfaces,shell interfaces on multiple display devices, and so forth.

According to various implementations, the tab environment 126 may berestored to a previous state by restoring characteristics of the tabenvironment 126, e.g., position, size, tab groups, user settings, devicesettings, and so forth. For instance, the previous state of the tabenvironment 126 and/or the task group 210 may include device-specificfeatures such as a multi-display device configuration, a mobileconfiguration, and so forth. In order to restore the previous state ofthe tab environment 126, the tab environment module 128 and/or the taskgroup module 124 may collapse more than one shell interface into asingle shell interface with multiple tabs or expand one shell interfacewith multiple tabs into more than one shell interface in someimplementations.

As illustrated in the scenario 400 b, the tab environment 126 may berestored to a previous state to surface the task group 210 via the shellinterfaces 404 a, 404 b. For example, consider a situation preceding thescenario 400 b in which the tab environment 126 was presented on boththe client device 102 and on a different device, e.g., on the otherclient device(s) 104. The scenario 400 b depicts the task group 210being surfaced to the tab environment 126 such that the tab environment126 is restored to the previous state in which the task group 210 waspresented across multiple devices. Since the task group 210 waspreviously presented on separate devices and in separate shellinterfaces, the tab environment 126 is presented on the single clientdevice 102 via the shell interfaces 404 a and 404 b to restore theprevious state. Although the shell interfaces 404 a and 404 b werepreviously presented in the described situation across different devicesas separate instances of the tab environment 126, the tab environment126 is restored to the single client device 102, as shown in thescenario 400 b. Thus, by surfacing the task group 210 into variousconfiguration of the tab environment 126 via the shell interfaces 404,the task group module 124 causes presentation of the task group 210 in aconvenient and intuitive manner across different device, display, andpresentation configurations.

FIG. 5 depicts an example implementation scenario 500 for creating atask group from task-related interaction in accordance with one or moreimplementations. The scenario 500 includes various entities andcomponents introduced above with reference to the environment 100 and inat least some implementations represents an alternative to the scenario200 or an extension of the scenarios 200, 300, 400 a, and 400 b.

In the scenario 500, the user 118 provides an input 502 to interact withthe source content 202 of the source application 114 and the targetcontent 208 of the target application 116. As depicted in the scenario,the source application 114 and the target application 116 are presentedin separate shell interfaces on the GUI 138. The task group module 124detects that interaction with the source content 202 and the targetcontent 208 (e.g., heterogeneous content) includes the input 502indicating that the interaction is task-related. Generally, the input502 represents an input or pattern of inputs detected by the task groupmodule 124 that indicate task-related interaction. In at least someimplementations, the input 502 indicates task-related interaction basedon frequency of occurrence and/or duration of the interaction withheterogeneous content such as the source content 202 and the targetcontent 208. For instance, the input 502 is detected when the user 118repeatedly switches focus between the source application 114 and thetarget application 116 in a task-related manner via the input mechanisms122. The input 502 may indicate task-related interaction based onvarious attributes of the input 502, such as copy, cutting, or pastingbetween the source application 114 and the target application 116,switching a shell interface focus between the source application 114 andthe target application 116, dragging a shell interface for anapplication 112 into the tab environment 126, and so forth.

In response to detecting the input 502 indicating the task-relatedinteraction, the task group module 124 creates the task group 210 toinclude the source content 202 and the target content 208. Consider anexample where the source application 114 is a word processingapplication and the target application 116 is a web browser application.Further, the user 118 is writing a paper in the source application 114and researching the topic of the paper in the target application 116.Continuing the example, the user 118 repeatedly copies and pastes thetarget content 208 from the web browser (the target application 116)into the word processing document (the source content 202 of the sourceapplication 114). In this example, the copy and paste activity (e.g.,interaction including the input 502) occurs for a predetermined numberof occurrences and/or a predetermined duration and the task group module124 determines the input 502 indicates task-related interaction andcreates the task group 210 to include the source application 114 and thetarget application 116. In at least some implementations, the sourceapplication 114 and the target application 116 are presented viadifferent display devices, such as in a multi-display configuration.

Having discussed some example implementation scenarios, consider now adiscussion of some example procedures in accordance with one or moreembodiments. The example procedures may be employed in the environment100 of FIG. 1, the system 900 of FIG. 9 and/or any other suitableenvironment. The procedures, for instance, represent example proceduresfor implementing the implementation scenarios described above. In atleast some implementations, the steps described for the variousprocedures are implemented automatically and independent of userinteraction. According to various implementations, the procedures may beperformed locally (e.g., at the client device 102), at a network-basedservice (e.g., at the network services 108), and/or via cooperationbetween the client device 102 and a network-based service.

FIG. 6 is a flow diagram that describes steps in a method for creatingand surfacing a task group in accordance with one or moreimplementations. In at least some implementations, the method can beperformed at least in part at the client device 102, e.g., by the taskgroup module 124 and/or the tab environment module 128.

Step 600 receives a request from a source application to launch targetcontent from a target application. The user 118, for instance, interactswith the client device 102 to perform an action to initiate launchingthe target content 208 from the source application 114. An example ofsuch an action includes selecting the visual indicator 204 (e.g., anicon) via the input mechanisms 122.

Step 602 presents a first instance of a heterogeneous tab environmentincluding a first tab populated by the source application selectable topresent source content and a second tab populated by the targetapplication presenting the target content. The tab environment 126, forinstance, is presented in the GUI 138 by the tab environment module 128in response to receiving the request 206. In various implementations,the tab environment 126 includes the tab 136 a populated with the sourceapplication 114 and selectable to display the source content 202, andthe tab 136 b is populated with the target application 116 displayingthe target content 208.

Step 604 creates a task group including the source content and thetarget content. The task group module 124, for example, creates the taskgroup 210 to include the source content 202 and the target content 208in response to receiving the request 206.

Step 606 receives an indication that one or more of the first tab or thesecond tab are closed. For example, the tab environment module 128notifies the task group module 124 that the tab environment 126 wasclosed by the user 118. In at least some implementations, the tabs 136 aand/or 136 b were closed individually and at different times.Additionally or alternatively, the tabs 136 a and/or 136 b were closedas a result of the tab environment 126 being closed.

Step 608 updates the task group to include relevant content from one ormore tabs which were open concurrently with the first tab or the secondtab. The task group module 124, for instance, queries the tabenvironment module 128 for content open concurrently with the sourcecontent 202 and/or the target content 208 in the tab environment 126.Upon receiving the relevant content 302, the task group module 124updates the task group 210 to include the relevant content 302. Byincluding the relevant content 302 in the task group, the task groupmodule 124 enables surfacing of the task group 210 in the tabenvironment 126, saving the user 118 from individually searching foreach of the source content 202, the target content 208, and the relevantcontent 302 to resume a task in which the user was engaged when the taskgroup 210 was created.

In one or more implementations, the task group module 124 identifies thetrigger event 212 for surfacing the task group 210. For instance, thetrigger event 212 is implemented as a request to launch the sourcecontent 202, the target content 208, and/or the relevant content 302 bythe user 118. In some implementations, the trigger event 212 may takethe form of a time-based event or a location-based event.

Responsive to receiving an indication of a trigger event, step 610surfaces the task group for presentation in a second instance of theheterogeneous tab environment configured to display the source content,the target content, and the relevant content each in individual tabs.For example, the task group module 124 receives a request to launch thesource content 202 and identifies the request as the trigger event 212.In at least some implementations, the task group module 124 surfaces thetask group 210 to the tab environment module 128 to cause the tabenvironment 126 to be populated with the task group 210, e.g., thesource content 202, the target content 208, and the relevant content.While in other implementations, more than one instance of the tabenvironment 126 is populated with the task group 210, e.g., the tabenvironment 126 is presented as two instances via the shell interfaces404 a and 404 b.

Additionally or alternatively, responsive to receiving the indication ofthe trigger event 212, the task group module 124 may cause presentationof the visual prompt 402 to the user 118. For instance, responsive toreceiving the indication of the trigger event 212, the task group module124 may cause presentation of the visual prompt 402 configured as aninteractive control displaying a selectable list of the instances ofcontent from the task group 210. Via interaction with the visual prompt402 the user 118 can individually select an instance of the sourcecontent 202, the target content 208, and/or the relevant content 302 tosurface in the tab environment 126. Accordingly, the user 118 maycontrol how much of the task group 210 to surface in the tab environment126.

FIG. 7 is a flow diagram that describes steps in a method for creating atask group in a heterogeneous tab environment in accordance with one ormore implementations. In at least some implementations, the method canbe performed at least in part at the client device 102, e.g., by thetask group module 124 and/or the tab environment module 128.

Step 700 receives a request from a source application to launch targetcontent from a target application. The user 118, for instance, selectsthe visual indicator 204 configured as an access protocol (e.g., URL)from the source application 114. The request 206 to launch the targetcontent 208 may be received by the task group module 124 in various waysas described above. For instance, the request may be received as amodified input from the input mechanisms 122 (e.g., a right-click orctrl-click from a mouse or touch input). Additionally or alternatively,the action to initiate launching the visual indicator 204 may beconfigured as a file association image (e.g., icon) or a file protocol(e.g., URI or URL).

Step 702 presents a heterogeneous tab environment including a sourcecontent tab selectable to display source content and a target contenttab displaying the target content. For example, the tab environmentmodule 128 presents the tab environment 126 including the tabs 136 a and136 b in the GUI 138. In at least some implementations, the tabenvironment 126 is presented in the shell interface of the sourceapplication 114. While in other implementations, the tab environment 126is presented in a new shell interface.

While web browser applications are conventionally associated with a tabenvironment, it should be understood that the applications 112, such asthe source application 114 and the target application 116 may be anytype of application including but not limited to a web browserapplication.

Step 704 creates a task group including the source content, the targetcontent, and relevant content collected from tabs open concurrently withthe source content tab or the target content tab in the heterogeneoustab environment, the task group enabling the source content, the targetcontent, and the relevant content to be surfaced together as individualtabs in a new instance of the heterogeneous tab environment. The taskgroup module 124, for instance, queries the tab environment module 128for the relevant content 302 open concurrently in the tab environment126 with the source content 202 and/or the target content 208. Bycollecting the relevant content 302 and including the relevant content302 in the task group 210, the task group module 124 enables the user118 to surface contextually related application content when resuming atask.

FIG. 8 is a flow diagram that describes steps in a method for creating atask group from task-related interaction in accordance with one or moreimplementations. In at least some implementations, the method can beperformed at least in part at the client device 102, e.g., by the taskgroup module 124 and/or the tab environment module 128.

Step 800 detects that interaction with heterogeneous content presentedfrom more than one application includes an input or pattern of inputsindicating that the interaction is task-related. For instance, more thanone of the applications 112 are presented in separate shell interfacesof the GUI 138. According to various implementations, the task groupmodule 124 detects interaction with the applications 112 by the user 118including the input 502 indicating that the interaction is task-related.The input 502 may indicate that an interaction with the source content202 and the target content 208 is task-related when the source content202 and the target content 208 are interacted with at a thresholdfrequency or in a manner that is task-related. For example, the input502 of copying, cutting, or pasting actions between the source content202 and target content 208 indicates task-related interaction when theinteraction is detected within or for a predetermined amount of time. Asanother example, the input 502 consisting of moving or dragging a shellinterface of an application 112 into the tab environment 126 to create anew tab may indicate task-related interaction.

Step 802 creates, responsive to detecting that the interaction istask-related, a task group including the heterogeneous content. The taskgroup module 124, for example, creates the task group 210 to include thesource content 202 and the target content 208 in response to detectingthat the interaction includes the input 502 indicating task-relatedinteraction.

Responsive to detecting a trigger event for the task group, step 804presents a heterogeneous tab environment configured to displayindividual tabs populated with different respective instances of theheterogeneous content. The task group module 124, for example, presentsthe tab environment 126 populated with the task group 210 in the tabs136 a, 136 b, and 136 c. The task group module 124, by presenting thetask group 210 in the tab environment 126, enables the user 118 tointeract with the source content 202, the target content 208, and therelevant content 302 in a single shell interface.

Having described some example procedures, consider now an example systemand device on which the various implementation scenarios and proceduresmay be implemented.

FIG. 9 illustrates an example system generally at 900 that includes anexample computing device 902 that is representative of one or morecomputing systems and/or devices that may implement various techniquesdescribed herein. For example, the client device 102 discussed abovewith reference to FIG. 1 can be embodied as the computing device 902.The computing device 902 may be, for example, a server of a serviceprovider, a device associated with the client (e.g., a client device),an on-chip system, and/or any other suitable computing device orcomputing system.

The example computing device 902 as illustrated includes a processingsystem 904, one or more computer-readable media 906, and one or moreInput/Output (I/O) Interfaces 908 that are communicatively coupled, oneto another. Although not shown, the computing device 902 may furtherinclude a system bus or other data and command transfer system thatcouples the various components, one to another. A system bus can includeany one or combination of different bus structures, such as a memory busor memory controller, a peripheral bus, a universal serial bus, and/or aprocessor or local bus that utilizes any of a variety of busarchitectures. A variety of other examples are also contemplated, suchas control and data lines.

The processing system 904 is representative of functionality to performone or more operations using hardware. Accordingly, the processingsystem 904 is illustrated as including hardware element 910 that may beconfigured as processors, functional blocks, and so forth. This mayinclude implementation in hardware as an application specific integratedcircuit or other logic device formed using one or more semiconductors.The hardware elements 910 are not limited by the materials from whichthey are formed or the processing mechanisms employed therein. Forexample, processors may be comprised of semiconductor(s) and/ortransistors (e.g., electronic integrated circuits (ICs)). In such acontext, processor-executable instructions may beelectronically-executable instructions.

The computer-readable media 906 is illustrated as includingmemory/storage 912. The memory/storage 912 represents memory/storagecapacity associated with one or more computer-readable media. Thememory/storage 912 may include volatile media (such as random accessmemory (RAM)) and/or nonvolatile media (such as read only memory (ROM),Flash memory, optical disks, magnetic disks, and so forth). Thememory/storage 912 may include fixed media (e.g., RAM, ROM, a fixed harddrive, and so on) as well as removable media (e.g., Flash memory, aremovable hard drive, an optical disc, and so forth). Thecomputer-readable media 906 may be configured in a variety of other waysas further described below.

Input/output interface(s) 908 are representative of functionality toallow a user to enter commands and information to computing device 902,and also allow information to be presented to the user and/or othercomponents or devices using various input/output devices. Examples ofinput devices include a keyboard, a cursor control device (e.g., amouse), a microphone (e.g., for voice recognition and/or spoken input),a scanner, touch functionality (e.g., capacitive or other sensors thatare configured to detect physical touch), a camera (e.g., which mayemploy visible or non-visible wavelengths such as infrared frequenciesto detect movement that does not involve touch as gestures), and soforth. Examples of output devices include a display device (e.g., amonitor or projector), speakers, a printer, a network card,tactile-response device, and so forth. Thus, the computing device 902may be configured in a variety of ways as further described below tosupport user interaction.

Various techniques may be described herein in the general context ofsoftware, hardware elements, or program modules. Generally, such modulesinclude routines, programs, objects, elements, components, datastructures, and so forth that perform particular tasks or implementparticular abstract data types. The terms “module,” “functionality,”“entity,” and “component” as used herein generally represent software,firmware, hardware, or a combination thereof. The features of thetechniques described herein are platform-independent, meaning that thetechniques may be implemented on a variety of commercial computingplatforms having a variety of processors.

An implementation of the described modules and techniques may be storedon or transmitted across some form of computer-readable media. Thecomputer-readable media may include a variety of media that may beaccessed by the computing device 902. By way of example, and notlimitation, computer-readable media may include “computer-readablestorage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices thatenable persistent storage of information in contrast to mere signaltransmission, carrier waves, or signals per se. Computer-readablestorage media do not include signals per se. The computer-readablestorage media includes hardware such as volatile and non-volatile,removable and non-removable media and/or storage devices implemented ina method or technology suitable for storage of information such ascomputer readable instructions, data structures, program modules, logicelements/circuits, or other data. Examples of computer-readable storagemedia may include, but are not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, hard disks, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or otherstorage device, tangible media, or article of manufacture suitable tostore the desired information and which may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing mediumthat is configured to transmit instructions to the hardware of thecomputing device 902, such as via a network. Signal media typically mayembody computer readable instructions, data structures, program modules,or other data in a modulated data signal, such as carrier waves, datasignals, or other transport mechanism. Signal media also include anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media include wired media such as awired network or direct-wired connection, and wireless media such asacoustic, radio frequency (RF), infrared, and other wireless media.

As previously described, hardware elements 910 and computer-readablemedia 906 are representative of instructions, modules, programmabledevice logic and/or fixed device logic implemented in a hardware formthat may be employed in some embodiments to implement at least someaspects of the techniques described herein. Hardware elements mayinclude components of an integrated circuit or on-chip system, anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), a complex programmable logic device (CPLD), and otherimplementations in silicon or other hardware devices. In this context, ahardware element may operate as a processing device that performsprogram tasks defined by instructions, modules, and/or logic embodied bythe hardware element as well as a hardware device utilized to storeinstructions for execution, e.g., the computer-readable storage mediadescribed previously.

Combinations of the foregoing may also be employed to implement varioustechniques and modules described herein. Accordingly, software,hardware, or program modules and other program modules may beimplemented as one or more instructions and/or logic embodied on someform of computer-readable storage media and/or by one or more hardwareelements 910. The computing device 902 may be configured to implementparticular instructions and/or functions corresponding to the softwareand/or hardware modules. Accordingly, implementation of modules that areexecutable by the computing device 902 as software may be achieved atleast partially in hardware, e.g., through use of computer-readablestorage media and/or hardware elements 910 of the processing system. Theinstructions and/or functions may be executable/operable by one or morearticles of manufacture (for example, one or more computing devices 902and/or processing systems 904) to implement techniques, modules, andexamples described herein.

As further illustrated in FIG. 9, the example system 900 enablesubiquitous environments for a seamless user experience when runningapplications on a personal computer (PC), a television device, and/or amobile device. Services and applications run substantially similar inall three environments for a common user experience when transitioningfrom one device to the next while utilizing an application, playing avideo game, watching a video, and so on.

In the example system 900, multiple devices are interconnected through acentral computing device. The central computing device may be local tothe multiple devices or may be located remotely from the multipledevices. In one embodiment, the central computing device may be a cloudof one or more server computers that are connected to the multipledevices through a network, the Internet, or other data communicationlink.

Discussed herein are a number of methods that may be implemented toperform techniques discussed herein. Aspects of the methods may beimplemented in hardware, firmware, or software, or a combinationthereof. The methods are shown as a set of steps that specify operationsperformed by one or more devices and are not necessarily limited to theorders shown for performing the operations by the respective blocks.Further, an operation shown with respect to a particular method may becombined and/or interchanged with an operation of a different method inaccordance with one or more implementations. Aspects of the methods canbe implemented via interaction between various entities discussed abovewith reference to the environment 100.

In the discussions herein, various different embodiments are described.It is to be appreciated and understood that each embodiment describedherein can be used on its own or in connection with one or more otherembodiments described herein. Further aspects of the techniquesdiscussed herein relate to one or more of the following embodiments.

A system for surfacing a task group in a tab environment, the systemcomprising: at least one processor; and one or more computer-readablestorage media including instructions stored thereon that, responsive toexecution by the at least one processor, cause the system to performoperations including: receiving a request from a source application tolaunch target content from a target application; presenting a firstinstance of a heterogeneous tab environment including a first tabpopulated by the source application selectable to present source contentand a second tab populated by the target application presenting thetarget content; creating a task group including the source content andthe target content; receiving an indication that one or more of thefirst tab or the second tab are closed; updating the task group toinclude relevant content from one or more tabs which were openconcurrently with the first tab or the second tab; and responsive toreceiving an indication of a trigger event, surfacing the task group forpresentation in a second instance of the heterogeneous tab environmentconfigured to display the source content, the target content, and therelevant content each in individual tabs.

In addition to any of the above described systems, any one orcombination of: wherein said receiving the indication of the triggerevent includes receiving a request to launch the source content, thetarget content, or the relevant content; wherein the operations furtherinclude determining the trigger event based at least in part on a date,time, location, or device contextually associated with the task group;wherein said surfacing the task group includes presenting a visualnotification selectable to cause presentation of the second instance ofthe heterogeneous tab environment configured to display the task group;wherein said surfacing the task group includes presenting an interactivecontrol configured to display selectable representations of eachinstance of the source content, the target content, and the relevantcontent individually for presentation in the second instance of theheterogeneous tab environment; wherein the operations further includedetermining the trigger event based on the target content, the sourcecontent, and the relevant content; wherein the trigger event is atime-based event; and wherein the trigger event is a location-basedevent.

A computer-implemented method for surfacing a task group in a tabenvironment, the method comprising: receiving a request from a sourceapplication to launch target content from a target application;presenting a heterogeneous tab environment including a source contenttab selectable to display source content and a target content tabdisplaying the target content; and creating a task group including thesource content, the target content, and relevant content collected fromtabs open concurrently with the source content tab or the target contenttab in the heterogeneous tab environment, the task group enabling thesource content, the target content, and the relevant content to besurfaced together as individual tabs in a new instance of theheterogeneous tab environment.

In addition to any of the above described systems, any one orcombination of: wherein the heterogeneous tab environment is presentedin a shell interface of the source application; wherein said receivingthe request at the source application to launch the target contentcomprises receiving a modified input selecting the target content, themodified input configured to launch the target content into a new shellinterface or a new tab; wherein said receiving the request at the sourceapplication to launch the target content comprises receiving an inputselecting a file association image or a file protocol for the targetcontent; wherein the source application or the target application is nota web browser; and wherein the target application is not locallyexecutable and wherein the method further comprises initiating aninstallation of a local instance of the target application.

A computer-implemented method for surfacing a task group in a tabenvironment, the method comprising: detecting that interaction withheterogeneous content presented from more than one application includesan input or pattern of inputs indicating that the interaction istask-related; creating, responsive to detecting that the interaction istask-related, a task group including the heterogeneous content; andresponsive to detecting a trigger event for the task group, presenting aheterogeneous tab environment configured to display individual tabspopulated with different respective instances of the heterogeneouscontent.

In addition to any of the above described systems, any one orcombination of: wherein the input or the pattern of inputs includescopying, cutting, or pasting actions between instances of theheterogeneous content occurring more than a threshold quantity for apredetermined amount of time; wherein the input or the pattern of inputsincludes switching a graphical user interface focus between instances ofthe heterogeneous content more than a threshold quantity for apredetermined amount of time; wherein the task group is created inresponse to an explicit request; further comprising presenting aninteractive control displaying visual representations for each instanceof the heterogeneous content and each instance of the relevant contentselectable to cause said presenting the heterogeneous tab environmentconfigured to display individual tabs populated from each selectedinstance; and wherein the input or pattern of inputs comprises moving ordragging an application shell interface into a tab environment as a newtab.

Techniques for surfacing a task group in a tab environment aredescribed. Although embodiments are described in language specific tostructural features and/or methodological acts, it is to be understoodthat the embodiments defined in the appended claims are not necessarilylimited to the specific features or acts described. Rather, the specificfeatures and acts are disclosed as example forms of implementing theclaimed embodiments.

What is claimed is:
 1. A system comprising: at least one processor; andone or more computer-readable storage media including instructionsstored thereon that, responsive to execution by the at least oneprocessor, cause the system to perform operations including: receiving arequest from a source application to launch target content from a targetapplication; presenting a first instance of a heterogeneous tabenvironment including a first tab populated by the source applicationselectable to present source content and a second tab populated by thetarget application presenting the target content; creating a task groupincluding the source content and the target content; receiving anindication that one or more of the first tab or the second tab areclosed; updating the task group to include relevant content from one ormore tabs which were open concurrently with the first tab or the secondtab; and responsive to receiving an indication of a trigger event,surfacing the task group for presentation in a second instance of theheterogeneous tab environment configured to display the source content,the target content, and the relevant content each in individual tabs. 2.The system described in claim 1, wherein said receiving the indicationof the trigger event includes receiving a request to launch the sourcecontent, the target content, or the relevant content.
 3. The systemdescribed in claim 1, wherein the operations further include determiningthe trigger event based at least in part on a date, time, location, ordevice contextually associated with the task group.
 4. The systemdescribed in claim 1, wherein said surfacing the task group includespresenting a visual notification selectable to cause presentation of thesecond instance of the heterogeneous tab environment configured todisplay the task group.
 5. The system described in claim 1, wherein saidsurfacing the task group includes presenting an interactive controlconfigured to display selectable representations of each instance of thesource content, the target content, and the relevant contentindividually for presentation in the second instance of theheterogeneous tab environment.
 6. The system describes in claim 1,wherein the operations further include determining the trigger eventbased on the target content, the source content, and the relevantcontent.
 7. The system described in claim 1, wherein the trigger eventis a time-based event.
 8. The system described in claim 1, wherein thetrigger event is a location-based event.
 9. A computer-implementedmethod comprising: receiving a request from a source application tolaunch target content from a target application; presenting aheterogeneous tab environment including a source content tab selectableto display source content and a target content tab displaying the targetcontent; and creating a task group including the source content, thetarget content, and relevant content collected from tabs openconcurrently with the source content tab or the target content tab inthe heterogeneous tab environment, the task group enabling the sourcecontent, the target content, and the relevant content to be surfacedtogether as individual tabs in a new instance of the heterogeneous tabenvironment.
 10. The method described in claim 9, wherein theheterogeneous tab environment is presented in a shell interface of thesource application.
 11. The method described in claim 9, wherein saidreceiving the request at the source application to launch the targetcontent comprises receiving a modified input selecting the targetcontent, the modified input configured to launch the target content intoa new shell interface or a new tab.
 12. The method described in claim 9,wherein said receiving the request at the source application to launchthe target content comprises receiving an input selecting a fileassociation image or a file protocol for the target content.
 13. Themethod described in claim 9, wherein the source application or thetarget application is not a web browser.
 14. The method described inclaim 9, wherein the target application is not locally executable andwherein the method further comprises initiating an installation of alocal instance of the target application.
 15. A computer-implementedmethod comprising: detecting that interaction with heterogeneous contentpresented from more than one application includes an input or pattern ofinputs indicating that the interaction is task-related; creating,responsive to detecting that the interaction is task-related, a taskgroup including the heterogeneous content; and responsive to detecting atrigger event for the task group, presenting a heterogeneous tabenvironment configured to display individual tabs populated withdifferent respective instances of the heterogeneous content.
 16. Themethod described in claim 15, wherein the input or the pattern of inputsincludes copying, cutting, or pasting actions between instances of theheterogeneous content occurring more than a threshold quantity for apredetermined amount of time.
 17. The method described in claim 15,wherein the input or the pattern of inputs includes switching agraphical user interface focus between instances of the heterogeneouscontent more than a threshold quantity for a predetermined amount oftime.
 18. The method described in claim 15, wherein the task group iscreated in response to an explicit request.
 19. The method described inclaim 15, further comprising presenting an interactive controldisplaying visual representations for each instance of the heterogeneouscontent and each instance of the relevant content selectable to causesaid presenting the heterogeneous tab environment configured to displayindividual tabs populated from each selected instance.
 20. The methoddescribed in claim 15, wherein the input or pattern of inputs comprisesmoving or dragging an application shell interface into a tab environmentas a new tab.